Download Professional Scrum Master I.PSM-I.Actual4Test.2026-11-10.98q.vcex

A scrum master is a coach and a facilitator while a traditional project manager is the one who manages a project in terms of scope, timelines, resources, budget and amount of work. A PM's focus is on Project while a Scrum Master's focus is on Team and Team members.

According to the Scrum Guide, changing the terminology of Scrum may have negative consequences, such as losing the benefits of Scrum, not understanding what has changed, or having very little change at all.Therefore, all answers apply to this question. The Scrum Guide recommends using the same terminology as in the guide to avoid confusion and misunderstanding.

When multiple Scrum Teams work on the same product, they should share a common Definition of Done. This creates transparency across the product and ensures that all Increments are held to the same quality standard. Without one shared Definition of Done, it becomes difficult to inspect the integrated product accurately and determine whether work is truly complete.

If stakeholders are dissatisfied with quality, the Product Owner should ensure that quality expectations are transparent. Product Backlog items can include quality-related requirements, acceptance criteria, or other specifications. The Developers also need to understand the stakeholder feedback so they can inspect and adapt.The Scrum Master serves the Product Owner by helping them communicate effectively with the Developers and facilitating resolution of impediments and concerns. Rather than solving the problem alone, the Scrum Master helps the Product Owner and Developers collaborate on addressing the quality issue.

According to the Scrum Guide, Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques. Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.

The Development Team must do as much work as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of "Done", as stated in the Scrum Guide 1 :"The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal. The entire Scrum Team collaborates on understanding the work of the Sprint."

According to the Scrum Guide, estimates are made by the people doing the work, which is the Development Team. The Development Team is responsible for all estimates in the Product Backlog and the Sprint Backlog.The other options are not valid guidelines for estimating work in Scrum, as they are either too prescriptive (such as requiring story points or relative units), incorrect (such as forbidding estimating or having the Product Owner make estimates), or unnecessary (such as checking estimates with the Development Team).